Download Oracle Database 12c: Data Guard Administration.1z0-066.PassCertification.2020-01-27.67q.vcex

Vendor: Oracle
Exam Code: 1z0-066
Exam Name: Oracle Database 12c: Data Guard Administration
Date: Jan 27, 2020
File Size: 270 KB
Downloads: 3
Download Exam

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase
Coupon: EXAMFILESCOM

Discount: 20%

ProfExam Simulator ProfExam Simulator ProfExam Simulator ProfExam Simulator ProfExam Simulator

Demo Questions

Question 1
Which two statements are true for Data Guard environments with multi-tenant databases? (Choose two.)
  1. DB_UNIQUE_NAME must be specified differently for each pluggable database within a multi-tenant standby database.
  2. Each pluggable database within a multi-tenant physical standby database has a minimum of one associated Oracle Net service name.
  3. Each pluggable database within a multi-tenant physical standby has one MRP background process running during redo apply.
  4. A pluggable database within a multi-tenant standby database can have a different open mode than the container database.
  5. A pluggable database within a multi-tenant standby database can have a different database role than the container database.
Correct answer: AD
Explanation:
Incorrect Answers:C: in 12c Data Guard is set up at the Container level and not the individual Pluggable database level as the redo log files only belong to the Container database and the individual pluggable databases do not have their own online redo log files.E: The database role is defined at the CDB level, not at the individual container level.Any DDL related to role changes must be executed in the root container because a role is associated with an entire CDB. Individual pluggable databases (PDBs) do not have their own roles. Reference: https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB5213
Incorrect Answers:
C: in 12c Data Guard is set up at the Container level and not the individual Pluggable database level as the redo log files only belong to the Container database and the individual pluggable databases do not have their own online redo log files.
E: The database role is defined at the CDB level, not at the individual container level.
Any DDL related to role changes must be executed in the root container because a role is associated with an entire CDB. Individual pluggable databases (PDBs) do not have their own roles. 
Reference: https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB5213
Question 2
Your Data Guard environment has two remote physical standby databases. 
Client applications use the local naming method to connect to the primary database instance. 
You want applications to automatically connect to the new primary database instance in case of a switchover or a failover. 
Which will fulfill this requirement?
  1. Create a database service on each standby database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors used by client applications to include all the standby hosts and connect to the database instance using that service name.
  2. Create a database service on the primary database that is started automatically by a trigger, when the database role is PRIMARY; modify the connection descriptors used by client applications to include all the standby hosts and connect to the database instance using that service name.
  3. Set the INSTANCE_NAME parameter identically on all databases; modify the connection descriptor on client applications to include all the standby hosts and connect to the database instance using that service name.
  4. Set the DB_NAME and DB_UNIQUE_NAME identically on all databases; modify the connection descriptors on client applications to include all the standby hosts and connect to the database instance using that service name.
Correct answer: A
Explanation:
Reference: http://docs.oracle.com/cd/B19306_01/server.102/b14239/scenarios.htm#i1054744
Reference: http://docs.oracle.com/cd/B19306_01/server.102/b14239/scenarios.htm#i1054744
Question 3
Examine the Data Guard configuration:
DGMGRL> show configuration; 
Configuration ‒ Animals 
  Protection Mode: MaxPerformance
  Databases:
  dogs ‒ Primary database 
    sheep ‒ Snapshot standby database 
    cats ‒ Snapshot standby database 
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS 
You receive an error while attempting to raise the protection mode to Maximum Availability:
DGMGDRL> edit configuration set protection mode as maxavailability; 
Error: ORA-16627: operation disallowed since no standby databases would remain to support protection mode 
Failed. 
Identify two statements that you can execute, either one of which will enable successful raising of the protection mode to Maximum Availability. (Choose two.)
  1. DGMGRL> convert database sheep to physical standby;
  2. DGMGRL> convert database cats to physical standby;
  3. DGMGRL> edit database dogs set property LogXptMode= fastsync;
  4. DGMGRL> edit database sheep set property LogXptMode= fastsync;
  5. DGMGRL> edit database cats set property LogXptMode= sync;
Correct answer: DE
Question 4
Which two are prerequisites for configuring flashback database for Oracle 12c databases, in a Data Guard environment? (Choose two.)
  1. A flash recovery area must be configured.
  2. The database must be in MOUNT state.
  3. The database must be in ARCHIVELOG mode.
  4. A far sync instance must be configured to flash back a standby when the primary has been flashed back.
  5. The Data Guard Broker must be used.
Correct answer: AC
Explanation:
Configure the following database settings before enabling Flashback Database:You must have a fast recovery area enabled, because flashback logs can only be stored in the fast recovery area. Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation. For Oracle Real Application Clusters (Oracle RAC) databases, the fast recovery area must be in a clustered file system or in ASM. Reference: https://docs.oracle.com/database/121/BRADV/flashdb.htm#BRADV582
Configure the following database settings before enabling Flashback Database:
You must have a fast recovery area enabled, because flashback logs can only be stored in the fast recovery area. 
Your database must be running in ARCHIVELOG mode, because archived logs are used in the Flashback Database operation. 
For Oracle Real Application Clusters (Oracle RAC) databases, the fast recovery area must be in a clustered file system or in ASM. 
Reference: https://docs.oracle.com/database/121/BRADV/flashdb.htm#BRADV582
Question 5
Which four database parameters might be affected by or influence the creation of standby databases? (Choose four.)
  1. DB_NAME
  2. ARCHIVE_LAG_TARGET
  3. COMPATIBLE
  4. DB_FILE_NAME_CONVERT
  5. DB_UNIQUE_NAME
  6. FAL_SERVER
  7. STANDBY_ARCHIVE_DEST
Correct answer: ADEF
Explanation:
A: DB_NAMEOn a primary database, specify the name used when the database was created. On a physical standby database, use the DB_NAME of the primary database. C: Ensure the COMPATIBLE initialization parameter is set to the same value on both the primary and standby databases. If the values differ, redo transport services may be unable to transmit redo data from the primary database to the standby databases.D: DB_FILE_NAME_CONVERTSpecify the path name and filename location of the primary database data files followed by the standby location. This parameter converts the path names of the primary database data files to the standby data file path names. E: DB_UNIQUE_NAMESpecify a unique name for each database. This name stays with the database and does not change, even if the primary and standby databases reverse roles. F: FAL_SERVERSpecify the Oracle Net service name of the FAL server (typically this is the database running in the primary role). Reference: https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB4720
A: DB_NAME
On a primary database, specify the name used when the database was created. On a physical standby database, use the DB_NAME of the primary database. 
C: Ensure the COMPATIBLE initialization parameter is set to the same value on both the primary and standby databases. If the values differ, redo transport services may be unable to transmit redo data from the primary database to the standby databases.
D: DB_FILE_NAME_CONVERT
Specify the path name and filename location of the primary database data files followed by the standby location. This parameter converts the path names of the primary database data files to the standby data file path names. 
E: DB_UNIQUE_NAME
Specify a unique name for each database. This name stays with the database and does not change, even if the primary and standby databases reverse roles. 
F: FAL_SERVER
Specify the Oracle Net service name of the FAL server (typically this is the database running in the primary role). 
Reference: https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB4720
Question 6
Your Data Guard environment has one physical standby database using Real-Time Query. 
Two sequences have been created by these SQL statements:
create sequence a global; 
create sequence b session; 
Neither sequence has been used since being created. 
Session 1 connects to the primary database instance and issues these two SQL statements:
SELECT a.nextval FROM DUAL; 
SELECT b.nextval FROM DUAL; 
Then session 2 connects to the physical standby database instance and issues the same SQL statements. 
What output will be seen for session 2?
  1.   
  2.   
  3.   
  4.   
Correct answer: A
Question 7
Examine the Data Guard configuration:
DGMGRL> show configuration; 
Configuration –Animals 
Protection Mode: MaxAvailability
  Databases:
  dogs- Primary database 
    cats- Snapshot standby database 
    sheep- Snapshot standby database 
Fast-Start Failover: DISABLED
Configuration Status:
ORA-01034: ORACLE not available
ORA-16625: cannot reach database “dogs”
DGM-17017: unable to determine configuration status
You wish to perform a failover to Sheep. 
Which command, or sequence of commands, should you issue to the broker before executing “failover to sheep”, using the broker?
  1. DGMGRL> convert database cats to physical standby;
  2. DGMGRL> convert database sheep to physical standby;
  3. DGMGRL> convert database sheep to physical standby; 
    DGMGRL> convert database cats to physical standby;
  4. DGMGRL>edit configuration set protection mode as maxperformance; 
    DGMGRL> convert database sheep to physical standby;
  5. None, because you can directly failover to a Snapshot Standby Database.
Correct answer: E
Question 8
Which four factors can influence the rate of SQL apply on a logical standby database? (Choose four.)
  1. the size of the undo tablespace on the logical standby database
  2. the number of full table scans performed by SQL apply
  3. the number of coordinator processes on the standby database instance
  4. the size of the shared pool
  5. the number of APPLIER processes
  6. the number of PREPARER processes
Correct answer: BDEF
Explanation:
B: If a table still does not have any unique index specified on the logical standby database, this may cause UPDATE statements to do full table scans on the logical standby database. You can remedy that by adding a unique index on the column on the logical standby database.E: SQL Apply uses a collection of background processes to apply changes from the primary database to the logical standby database.During apply processing:The ANALYZER process identifies dependencies between different transactions. The COORDINATOR process (LSP) assigns transactions to different appliers and coordinates among them to ensure that dependencies between transactions are honored. The APPLIER processes applies transactions to the logical standby database under the supervision of the coordinator process. F: The PREPARER process is used during the log mining process, which is part of the SQL apply process.D: The Shared Pool is used by the preparar and Builder proccesses.Figure: SQL Apply Processing    Incorrect Answers:C: There is only one coordinator process.Reference: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm
B: If a table still does not have any unique index specified on the logical standby database, this may cause UPDATE statements to do full table scans on the logical standby database. You can remedy that by adding a unique index on the column on the logical standby database.
E: SQL Apply uses a collection of background processes to apply changes from the primary database to the logical standby database.
During apply processing:
  • The ANALYZER process identifies dependencies between different transactions. 
  • The COORDINATOR process (LSP) assigns transactions to different appliers and coordinates among them to ensure that dependencies between transactions are honored. 
  • The APPLIER processes applies transactions to the logical standby database under the supervision of the coordinator process. 
F: The PREPARER process is used during the log mining process, which is part of the SQL apply process.
D: The Shared Pool is used by the preparar and Builder proccesses.
Figure: SQL Apply Processing
  
Incorrect Answers:
C: There is only one coordinator process.
Reference: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm
Question 9
There are currently 6 APPLIER and 6 PREPARER processes running and no idle APPLIER processes on your logical standby database. 
The MAX_SERVERS SQL apply parameter and number of archiver processes are both set to 12. 
Identify two changes, each of which would allow you to increase the number of APPLIER processes. (Choose two.)
  1. Increase the PROCESSES initialization parameter
  2. Increase the value for the MAX_SERVERS SQL apply parameter.
  3. Decrease the number of archiver processes on the standby database.
  4. Increase the PARALLEL_MAX_SERVER initialization parameter
  5. Decrease the number of PREPARER processes
  6. Increase the RECOVERY_PARALLELISM initialization parameter
Correct answer: BE
Explanation:
There are three parameters that can be modified to control the number of processes allocated to SQL Apply: MAX_SERVERS, APPLY_SERVERS, and PREPARE_SERVERS. The following relationships must always hold true:APPLY_SERVERS + PREPARE_SERVERS = MAX_SERVERS - 3 This is because SQL Apply always allocates one process for the READER, BUILDER, and ANALYZER roles. References: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm
There are three parameters that can be modified to control the number of processes allocated to SQL Apply: MAX_SERVERS, APPLY_SERVERS, and PREPARE_SERVERS. The following relationships must always hold true:
APPLY_SERVERS + PREPARE_SERVERS = MAX_SERVERS - 3 
This is because SQL Apply always allocates one process for the READER, BUILDER, and ANALYZER roles. 
References: https://docs.oracle.com/cd/B28359_01/server.111/b28294/manage_ls.htm
Question 10
Which three statements are true about snapshot standby databases? (Choose three.)
  1. Snapshot standby databases may be used for rolling release upgrades.
  2. If datafiles grow while a database is a snapshot standby database, then they shrink when converted back to a physical standby database.
  3. Flashback logs are used to convert a snapshot standby database back into a physical standby database.
  4. A snapshot standby database can have Real-Time Query enabled.
  5. A guaranteed restore point is created automatically when a physical standby database is converted into a snapshot standby database.
Correct answer: BCE
Explanation:
C: Flashback Database is similar to conventional point-in-time recovery in its effects. It enables you to return a database to its state at a time in the recent past. Flashback Database uses its own logging mechanism, creating flashback logs and storing them in the fast recovery area. You can only use Flashback Database if flashback logs are available. Flashback Database is used to convert a snapshot standby database back into a physical standby database.E: When we convert the physical standby database to snapshot standby database a guaranteed restore point is created. This guaranteed restore point is used to flashback a snapshot standby database to its original state.Incorrect Answers:A: Oracle Database supports the installation of database software upgrades, and the application of patch sets, in a rolling fashion—with near zero database downtime—by using Data Guard SQL Apply and logical standby databases.References:https://docs.oracle.com/cd/E11882_01/server.112/e41134/manage_ps.htm#SBYDB4803http://satya-dba.blogspot.se/2012/06/snapshot-standby-databases-oracle.html
C: Flashback Database is similar to conventional point-in-time recovery in its effects. It enables you to return a database to its state at a time in the recent past. Flashback Database uses its own logging mechanism, creating flashback logs and storing them in the fast recovery area. You can only use Flashback Database if flashback logs are available. Flashback Database is used to convert a snapshot standby database back into a physical standby database.
E: When we convert the physical standby database to snapshot standby database a guaranteed restore point is created. This guaranteed restore point is used to flashback a snapshot standby database to its original state.
Incorrect Answers:
A: Oracle Database supports the installation of database software upgrades, and the application of patch sets, in a rolling fashion—with near zero database downtime—by using Data Guard SQL Apply and logical standby databases.
References:
https://docs.oracle.com/cd/E11882_01/server.112/e41134/manage_ps.htm#SBYDB4803
http://satya-dba.blogspot.se/2012/06/snapshot-standby-databases-oracle.html
CONNECT US
HOW TO OPEN VCE FILES

Use VCE Exam Simulator to open VCE files
Avanaset

HOW TO OPEN VCEX AND EXAM FILES

Use ProfExam Simulator to open VCEX and EXAM files
ProfExam Screen

ProfExam
ProfExam at a 20% markdown

You have the opportunity to purchase ProfExam at a 20% reduced price

Get Now!